Operation of a multi-slice processor implementing tagged geometric history length branch prediction

ABSTRACT

Operation of a multi-slice processor implementing a tagged geometric history length prediction unit and an effective address table aligned with an update table, where the multi-slice processor includes a plurality of execution slices. Operation of such a multi-slice processor includes: receiving, at an effective address table and at a TAGE update table, information for a branch instruction dispatched to an execution slice, wherein the effective address table and the TAGE update table are in alignment; responsive to the branch instruction being taken, updating the effective address table and the TAGE update table to indicate the branch instruction being taken; and updating, in dependence upon the alignment between the effective address table and the TAGE update table, the TAGE branch prediction unit with update information from both the effective address table and the TAGE update table.

BACKGROUND Field of the Invention

The field of the invention is data processing, or, more specifically, methods and apparatus for operation of a multi-slice processor.

Description of Related Art

The development of the EDVAC computer system of 1948 is often cited as the beginning of the computer era. Since that time, computer systems have evolved into extremely complicated devices. Today's computers are much more sophisticated than early systems such as the EDVAC. Computer systems typically include a combination of hardware and software components, application programs, operating systems, processors, buses, memory, input/output devices, and so on. As advances in semiconductor processing and computer architecture push the performance of the computer higher and higher, more sophisticated computer software has evolved to take advantage of the higher performance of the hardware, resulting in computer systems today that are much more powerful than just a few years ago.

One area of computer system technology that has advanced is computer processors. As the number of computer systems in data centers and the number of mobile computing devices has increased, the need for more efficient computer processors has also increased. Speed of operation and power consumption are just two areas of computer processor technology that affect efficiency of computer processors.

SUMMARY

Methods and apparatus for operation of a multi-slice processor implementing a tagged geometric history length prediction unit and an effective address table aligned with an update table are disclosed in this specification. Such a multi-slice processor includes a plurality of execution slices and a plurality of load/store slices, where the load/store slices are coupled to the execution slices via a results bus. Such a multi-slice processor may further include a tagged geometric history length (TAGE) branch prediction unit. Operation of such a multi-slice processor includes: receiving, at an effective address table and at a TAGE update table, information for a branch instruction dispatched to an execution slice, wherein the effective address table and the TAGE update table are in alignment; responsive to the branch instruction being taken, updating the effective address table and the TAGE update table to indicate the branch instruction being taken; and updating, in dependence upon the alignment between the effective address table and the TAGE update table, the TAGE branch prediction unit with update information from both the effective address table and the TAGE update table.

The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular descriptions of exemplary embodiments of the invention as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts of exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 sets forth a block diagram of an example system configured for operation of a multi-slice processor according to embodiments of the present invention.

FIG. 2 sets forth a block diagram of a portion of a multi-slice processor according to embodiments of the present invention.

FIG. 3 sets forth a block diagram of a dispatch network configured to implement tagged geometric history length branch prediction according to different embodiments.

FIG. 4 sets forth a flow chart illustrating an exemplary method of operation of a multi-slice processor configured to implement tagged geometric history length branch prediction according to different embodiments.

FIG. 5 sets forth a flow chart illustrating an exemplary method of operation of a multi-slice processor configured to implement tagged geometric history length branch prediction according to different embodiments.

DETAILED DESCRIPTION

Exemplary methods and apparatus for operation of a multi-slice processor in accordance with the present invention are described with reference to the accompanying drawings, beginning with FIG. 1. FIG. 1 sets forth a block diagram of an example system configured for operation of a multi-slice processor according to embodiments of the present invention. The system of FIG. 1 includes an example of automated computing machinery in the form of a computer (152).

The computer (152) of FIG. 1 includes at least one computer processor (156) or ‘CPU’ as well as random access memory (168) (RAM′) which is connected through a high speed memory bus (166) and bus adapter (158) to processor (156) and to other components of the computer (152).

The example computer processor (156) of FIG. 1 may be implemented as a multi-slice processor. The term ‘multi-slice’ as used in this specification refers to a processor having a plurality of similar or identical sets of components, where each set may operate independently of all the other sets or in concert with the one or more of the other sets. The multi-slice processor (156) of FIG. 1, for example, includes several execution slices (ES′) and several load/store slices (‘LSS’)—where load/store slices may generally be referred to as load/store units. Each execution slice may be configured to provide components that support execution of instructions: an issue queue, general purpose registers, a history buffer, an arithmetic logic unit (including a vector scalar unit, a floating point unit, and others), and the like. Each of the load/store slices may be configured with components that support data movement operations such as loading of data from cache or memory or storing data in cache or memory. In some embodiments, each of the load/store slices includes a data cache. The load/store slices are coupled to the execution slices through a results bus. In some embodiments, each execution slice may be associated with a single load/store slice to form a single processor slice. In some embodiments, multiple processor slices may be configured to operate together.

The example multi-slice processor (156) of FIG. 1 may also include, in addition to the execution and load/store slices, other processor components. In the system of FIG. 1, the multi-slice processor (156) includes fetch logic, dispatch logic, and branch prediction logic. Further, although in some embodiments each load/store slice includes cache memory, the multi-slice processor (156) may also include cache accessible by any or all of the processor slices.

Although the multi-slice processor (156) in the example of FIG. 1 is shown to be coupled to RAM (168) through a front side bus (162), a bus adapter (158) and a high speed memory bus (166), readers of skill in the art will recognize that such configuration is only an example implementation. In fact, the multi-slice processor (156) may be coupled to other components of a computer system in a variety of configurations. For example, the multi-slice processor (156) in some embodiments may include a memory controller configured for direct coupling to a memory bus (166). In some embodiments, the multi-slice processor (156) may support direct peripheral connections, such as PCIe connections and the like.

Stored in RAM (168) in the example computer (152) is a data processing application (102), a module of computer program instructions that when executed by the multi-slice processor (156) may provide any number of data processing tasks. Examples of such data processing applications may include a word processing application, a spreadsheet application, a database management application, a media library application, a web server application, and so on as will occur to readers of skill in the art. Also stored in RAM (168) is an operating system (154). Operating systems useful in computers configured for operation of a multi-slice processor according to embodiments of the present invention include UNIX™, Linux™, Microsoft Windows™, AIX™, IBM's z/OS™, and others as will occur to those of skill in the art. The operating system (154) and data processing application (102) in the example of FIG. 1 are shown in RAM (168), but many components of such software typically are stored in non-volatile memory also, such as, for example, on a disk drive (170).

The computer (152) of FIG. 1 includes disk drive adapter (172) coupled through expansion bus (160) and bus adapter (158) to processor (156) and other components of the computer (152). Disk drive adapter (172) connects non-volatile data storage to the computer (152) in the form of disk drive (170). Disk drive adapters useful in computers configured for operation of a multi-slice processor according to embodiments of the present invention include Integrated Drive Electronics (‘IDE’) adapters, Small Computer System Interface (SCSI′) adapters, and others as will occur to those of skill in the art. Non-volatile computer memory also may be implemented for as an optical disk drive, electrically erasable programmable read-only memory (so-called ‘EEPROM’ or ‘Flash’ memory), RAM drives, and so on, as will occur to those of skill in the art.

The example computer (152) of FIG. 1 includes one or more input/output (′I/O′) adapters (178). I/O adapters implement user-oriented input/output through, for example, software drivers and computer hardware for controlling output to display devices such as computer display screens, as well as user input from user input devices (181) such as keyboards and mice. The example computer (152) of FIG. 1 includes a video adapter (209), which is an example of an I/O adapter specially designed for graphic output to a display device (180) such as a display screen or computer monitor. Video adapter (209) is connected to processor (156) through a high speed video bus (164), bus adapter (158), and the front side bus (162), which is also a high speed bus.

The exemplary computer (152) of FIG. 1 includes a communications adapter (167) for data communications with other computers (182) and for data communications with a data communications network (100). Such data communications may be carried out serially through RS-232 connections, through external buses such as a Universal Serial Bus (‘USB’), through data communications networks such as IP data communications networks, and in other ways as will occur to those of skill in the art. Communications adapters implement the hardware level of data communications through which one computer sends data communications to another computer, directly or through a data communications network. Examples of communications adapters useful in computers configured for operation of a multi-slice processor according to embodiments of the present invention include modems for wired dial-up communications, Ethernet (IEEE 802.3) adapters for wired data communications, and 802.11 adapters for wireless data communications.

The arrangement of computers and other devices making up the exemplary system illustrated in FIG. 1 are for explanation, not for limitation. Data processing systems useful according to various embodiments of the present invention may include additional servers, routers, other devices, and peer-to-peer architectures, not shown in FIG. 1, as will occur to those of skill in the art. Networks in such data processing systems may support many data communications protocols, including for example TCP (Transmission Control Protocol), IP (Internet Protocol), HTTP (HyperText Transfer Protocol), WAP (Wireless Access Protocol), HDTP (Handheld Device Transport Protocol), and others as will occur to those of skill in the art. Various embodiments of the present invention may be implemented on a variety of hardware platforms in addition to those illustrated in FIG. 1.

For further explanation, FIG. 2 sets forth a block diagram of a portion of a multi-slice processor according to embodiments of the present invention. The multi-slice processor in the example of FIG. 2 includes a dispatch network (202). The dispatch network (202) includes logic configured to dispatch instructions for execution among execution slices.

The multi-slice processor in the example of FIG. 2 also includes a number of execution slices (204 a, 204 b-204 n). Each execution slice includes general purpose registers (206) and a history buffer (208). The general purpose registers and history buffer may sometimes be referred to as the mapping facility, as the registers are utilized for register renaming and support logical registers.

The general purpose registers (206) are configured to store the youngest instruction targeting a particular logical register and the result of the execution of the instruction. A logical register is an abstraction of a physical register that enables out-of-order execution of instructions that target the same physical register.

When a younger instruction targeting the same particular logical register is received, the entry in the general purpose register is moved to the history buffer, and the entry in the general purpose register is replaced by the younger instruction. The history buffer (208) may be configured to store many instructions targeting the same logical register. That is, the general purpose register is generally configured to store a single, youngest instruction for each logical register while the history buffer may store many, non-youngest instructions for each logical register.

Each execution slice (204) of the multi-slice processor of FIG. 2 also includes an execution reservation station (210). The execution reservation station (210) may be configured to issue instructions for execution. The execution reservation station (210) may include an issue queue. The issue queue may include an entry for each operand of an instruction. The execution reservation station may issue the operands for execution by an arithmetic logic unit or to a load/store slice (222 a, 222 b, 222 c) via the results bus (220).

The arithmetic logic unit (212) depicted in the example of FIG. 2 may be composed of many components, such as add logic, multiply logic, floating point units, vector/scalar units, and so on. Once an arithmetic logic unit executes an operand, the result of the execution may be stored in the result buffer (214) or provided on the results bus (220) through a multiplexer (216).

The results bus (220) may be configured in a variety of manners and be of composed in a variety of sizes. In some instances, each execution slice may be configured to provide results on a single bus line of the results bus (220). In a similar manner, each load/store slice may be configured to provide results on a single bus line of the results bus (220). In such a configuration, a multi-slice processor with four processor slices may have a results bus with eight bus lines—four bus lines assigned to each of the four load/store slices and four bus lines assigned to each of the four execution slices. Each of the execution slices may be configured to snoop results on any of the bus lines of the results bus. In some embodiments, any instruction may be dispatched to a particular execution unit and then by issued to any other slice for performance. As such, any of the execution slices may be coupled to all of the bus lines to receive results from any other slice. Further, each load/store slice may be coupled to each bus line in order to receive an issue load/store instruction from any of the execution slices. Readers of skill in the art will recognize that many different configurations of the results bus may be implemented.

The multi-slice processor in the example of FIG. 2 also includes a number of load/store slices (222 a, 222 b-222 n). Each load/store slice includes a queue (224), a multiplexer (228), a data cache (232), and formatting logic (226), among other components described below with regard to FIG. 3. The queue receives load and store operations to be carried out by the load/store slice (222). The formatting logic (226) formats data into a form that may be returned on the results bus (220) to an execution slice as a result of a load or store instruction.

The example multi-slice processor of FIG. 2 may be configured for flush and recovery operations. A flush and recovery operation is an operation in which the registers (general purpose register and history buffer) of the multi-slice processor are effectively ‘rolled back’ to a previous state. The term ‘restore’ and ‘recover’ may be used, as context requires in this specification, as synonyms. Flush and recovery operations may be carried out for many reasons, including missed branch predictions, exceptions, and the like. Consider, as an example of a typical flush and recovery operation, that a dispatcher of the multi-slice processor dispatches over time and in the following order: an instruction A targeting logical register 5, an instruction B targeting logical register 5, and an instruction C targeting logical register 5. At the time instruction A is dispatched, the instruction parameters are stored in the general purpose register entry for logical register 5. Then, when instruction B is dispatched, instruction A is evicted to the history buffer (all instruction parameters are copied to the history buffer, including the logical register and the identification of instruction B as the evictor of instruction A), and the parameters of instruction B are stored in the general purpose register entry for logical register 5. When instruction C is dispatched, instruction B is evicted to the history buffer and the parameters of instruction C are stored in the general purpose register entry for logical register 5. Consider, now, that a flush and recovery operation of the registers is issued in which the dispatch issues a flush identifier matching the identifier of instruction C. In such an example, flush and recovery includes discarding the parameters of instruction C in the general purpose register entry for logical register 5 and moving the parameters of instruction B from the history buffer for instruction B back into the entry of general purpose register for logical register 5.

During the flush and recovery operation, in prior art processors, the dispatcher was configured to halt dispatch of new instructions to an execution slice. Such instructions may be considered either target or source instructions. A target instruction is an instruction that targets a logical register for storage of result data. A source instruction by contrast has, as its source, a logical register. A target instruction, when executed, will result in data stored in an entry of a register file while a source instruction utilizes such data as a source for executing the instruction. A source instruction, while utilizing one logical register as its source, may also target another logical register for storage of the results of instruction. That is, with respect to one logical register, an instruction may be considered a source instruction and with respect to another logical register, the same instruction may be considered a target instruction.

The multi-slice processor in the example of FIG. 2 also includes an instruction sequencing unit (240). While depicted within individual execution slices, in some cases, the instruction sequencing unit may be implemented independently of the execution slices or implemented within dispatch network (202). Instruction sequencing unit (240) may take dispatched instructions and check dependencies of the instructions to determine whether all older instructions with respect to a current instruction have delivered, or may predictably soon deliver, results of these older instructions from which the current instruction is dependent so that the current instruction may execute correctly. If all dependencies to a current instruction are satisfied, then a current instruction may be determined to be ready to issue, and may consequently be issued—regardless of a program order of instructions, where a program order may be determined by an ITAG. Such issuance of instructions may be referred to as an “out-of-order” execution, and the multi-slice processor may be considered an out-of-order machine.

In some cases, a load/store unit receiving an issued instruction, such as a load/store slice, may not yet be able to handle the instruction, and the instruction sequencing unit (240) may keep the instruction queued until such time as the load/store slice may handle the instruction. After the instruction is issued, the instruction sequencing unit (240) may track progress of the instruction based at least in part on signals received from a load/store slice.

For further explanation, FIG. 3 sets forth a block diagram of a portion of the dispatch network (202) of the multi-slice processor (156) implementing a tagged geometric history length prediction unit and an effective address table aligned with an update table. During normal operation, the dispatch network (202) receives computer instructions at an instruction fetch (302) unit, and, at the decode (304) unit, decodes and dispatches the computer instructions among the various execution slices (204 a, 204 b-204 n). Generally, these computer instructions correspond to software written by a user and compiled for the multi-slice processor (156).

Instruction fetch (302) unit may, in dependence upon a prediction generated and provided by a tagged geometric history length prediction unit, TAGE (306), determine which instructions to decode and dispatch to an execution slice in dependence upon a likelihood that a branch instruction within a sequence of instructions is predicted to be taken or not taken.

TAGE (306) may maintain multiple history lengths of varying, geometric lengths, that may be used for indexing into multiple different predictor tables, where the predictor tables may be maintained and updated according to a variety of techniques. Further, TAGE (306) may generate a predication based at least in part on information received from both a TAGE update table (310) and an effective address table (312).

Effective address table (312) may include entries (312 a-312 m) that store effective addresses for currently active instructions. Further, each entry for the effective address table (312), in addition to storing effective address information for an instruction, may store corresponding information indicating whether or not a branch is taken for the instruction.

TAGE update table (310) may include entries (310-a 1-310-m 4) such that each entry is aligned, or mapped to, a corresponding effective address entry within the effective address table (312). Further, each entry in the TAGE update table may store information corresponding to a branch prediction for an address specified according to a correspondingly mapped effective address for a branch instruction within the effective address table (312). Information stored within an entry of the TAGE update table (310) may include one or more of: a valid bit, a branch effective address, an indication as to whether a TAGE entry was hit, a TAGE component, a TAGE prediction, a TAGE usefulness indication, an alternative component, an alternative predication, a next component, and a next usefulness indication.

Branch execution (308) unit may receive information from both the effective address table (312) and one or more of the executions slices (204 a, 204 b-204 n) and provide the instruction fetch (302) unit with information regarding branches taken by instructions that have been executed, where the instruction fetch (302) unit may use the information received from the branch execution (308) unit, in conjunction with information from the TAGE (306), to determine instructions to fetch next.

For further explanation, FIG. 4 sets forth a flow chart illustrating an exemplary method of implementing a tagged geometric history length prediction unit and an effective address table aligned with an update table. The method of FIG. 4 may be carried out by a multi-slice processor similar to that in the examples of FIGS. 1-3. Such a multi-slice processor may include a dispatch network (202) that includes an effective address table (312), a TAGE update table (310), and a TAGE (306), as described above with regard to FIG. 3.

The method of FIG. 4 includes receiving (402), at the effective address table (312) and at the TAGE update table (310), information (452) for a branch instruction dispatched to an execution slice, where the effective address table (312) and the TAGE update table (310) are in alignment. Receiving (402) the information for the branch instruction may be carried out by the instruction fetch (302) unit of the dispatch network (202) providing, as depicted in FIG. 3, a branch instruction to both the TAGE update table (310) and the effective address table (312). The instruction from the instruction fetch (302) unit may also be provided to an execution slice, where the execution slice may—in executing one or more previous instructions—determine that a branch is to be taken or not. Further, information regarding taken or not taken branches may be provided from the execution slices back to the branch execution (308) unit.

The method of FIG. 4 also includes, responsive to the branch instruction being taken, updating (404) the effective address table (312) and the TAGE update table (310) to indicate the branch instruction being taken. Updating (404) the effective address table (312) and the TAGE update table (310) may be carried out by the instruction fetch (302) unit indexing an entry within the effective address table (312) corresponding to the effective address for the branch instruction, and updating the entry to indicate that the branch instruction resulted in a taken branch—where the instruction fetch (302) unit may receive information regarding the taken branch instruction from the branch execution (308) unit.

Similarly, updating the TAGE update table (310) may be carried out by the instruction fetch (302) unit indexing an entry within the TAGE update table (310) aligned to a corresponding entry within the effective address table (312) storing information for the branch instruction, and updating the entry in the TAGE update table (310) to indicate that the branch instruction resulted in a taken branch. Updating the TAGE update table (310) may further include updating one or more of the fields of the entry within the TAGE update table (310) for tracking a particular branch instruction, as described above.

An entry within the TAGE update table (310) may be considered to be aligned, or in alignment with, an entry in the effective address table (312) based at least on the corresponding entries being mapped to each other or based at least on the corresponding entries being similarly indexed. Generally, an entry in the TAGE update table (310) being aligned with, or in alignment with, an entry in the effective address table (310) refers to information within a single, particular location or entry of the TAGE update table (310) being mapped to a single, particular location or entry of the effective address table (312).

The method of FIG. 4 also includes updating (406), in dependence upon the alignment between the effective address table (312) and the TAGE update table (310), a TAGE branch prediction unit (306) with update information from both the effective address table (312) and the TAGE update table (310).

Updating (406) the TAGE (306) may be carried out by the TAGE (306)—in dependence upon the effective address table (312) providing effective address information for the branch instruction and the TAGE update table (310) providing information from an entry aligned, or mapped to, the entry or location in the effective address table (312) for the branch instruction using the information from both the effective address table (312) and the TAGE update table (312) to modify one or more predictor tables, or a base predictor. In other words, the effective address table may store effective addresses for instructions currently active, and the TAGE update table may store information for branches corresponding to a TAGE update.

For example, the TAGE update table (310) may provide, for a particular entry, one or more of: a valid bit, a branch effective address, an indication as to whether a TAGE entry was hit, a TAGE component, a TAGE prediction, a TAGE usefulness indication, an alternative component, an alternative predication, a next component, and a next usefulness indication.

In other words, a prediction of whether a subsequent branch instruction is taken is made in dependence upon updating the TAGE branch prediction unit and the update information. Further, in some cases, the update information is generated for the TAGE prediction unit without reading status information from the TAGE prediction unit.

In this way, based at least on the alignment between the TAGE update table (310) and the effective address table (312), where the alignment allows avoiding replication of stored data, the multi-slice processor may avoid extra logic within the TAGE (306) in order to update branch prediction components of a TAGE predictor.

For further explanation, FIG. 5 sets forth a flow chart illustrating an exemplary method of operation of a multi-slice processor implementing a tagged geometric history length prediction unit and an effective address table aligned with an update table. The method of FIG. 5 may be carried out by a multi-slice processor similar to that in the examples of FIGS. 1-3. Such a multi-slice processor may include a dispatch network (202) that includes an effective address table (312), a TAGE update table (310), and a TAGE (306), as described above with regard to FIG. 3.

The method of FIG. 5 is similar to the method of FIG. 4 in that the method of FIG. 5 also includes: receiving (402), at the effective address table (312) and at the TAGE update table (310), information for a branch instruction dispatched to an execution slice, where the effective address table (312) and the TAGE update table (310) are in alignment; responsive to the branch instruction being taken, updating (404) the effective address table (312) and the TAGE update table (310) to indicate the branch instruction being taken; and updating (406), in dependence upon the alignment between the effective address table (312) and the TAGE update table (310), a TAGE branch prediction unit (306) with update information from both the effective address table (312) and the TAGE update table (310).

The method of FIG. 5 differs from the method of FIG. 4, however, in that the method of FIG. 5 further includes generating (502), in dependence upon a mapping from an effective address table (312) location to the TAGE update table (310) location, update information (552) based on information from the effective address table location and on information from the TAGE update table (310) location. Generating (502) the update information may be carried out by the dispatch network (202) logic providing, to the TAGE (306), effective address information from the effective address table (312) for the branch instruction and providing information from an entry aligned, or mapped to, the location in the effective address table (312) for the branch instruction.

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims. 

What is claimed is:
 1. A method of operation of a multi-slice processor, the multi-slice processor including a plurality of execution slices and a tagged geometric history length (TAGE) branch prediction unit, wherein the method comprises: receiving, at an effective address table and at a TAGE update table, information for a branch instruction dispatched to an execution slice, wherein the effective address table and the TAGE update table are in alignment; responsive to the branch instruction being taken, updating the effective address table and the TAGE update table to indicate the branch instruction being taken; and updating, in dependence upon the alignment between the effective address table and the TAGE update table, the TAGE branch prediction unit with update information from both the effective address table and the TAGE update table.
 2. The method of claim 1, wherein the alignment between the effective address table and the TAGE update table is dependent upon each entry in the TAGE update table being mapped to a corresponding entry in the effective address table.
 3. The method of claim 1, further comprising: generating, in dependence upon a mapping from an effective address table location to a TAGE update table location, the update information based on information from the effective address table location and on information from the TAGE update table location.
 4. The method of claim 3, wherein the update information is generated for the TAGE prediction unit without reading status information from the TAGE prediction unit.
 5. The method of claim 1, wherein the update information includes one or more of: a valid bit, a branch effective address, an indication as to whether a TAGE entry was hit, a TAGE component, a TAGE prediction, a TAGE usefulness indication, an alternative component, an alternative predication, a next component, and a next usefulness indication.
 6. The method of claim 5, wherein a prediction of whether a subsequent branch instruction is taken is made in dependence upon updating the TAGE branch prediction unit and the update information.
 7. The method of claim 1, wherein the effective address table stores effective addresses for instructions currently active, and wherein the TAGE update table stores information for branches corresponding to a TAGE update.
 8. A multi-slice processor comprising: a plurality of execution slices, a tagged geometric history length (TAGE) branch prediction unit, wherein the multi-slice processor is configured to carry out: receiving, at an effective address table and at a TAGE update table, information for a branch instruction dispatched to an execution slice, wherein the effective address table and the TAGE update table are in alignment; responsive to the branch instruction being taken, updating the effective address table and the TAGE update table to indicate the branch instruction being taken; and updating, in dependence upon the alignment between the effective address table and the TAGE update table, the TAGE branch prediction unit with update information from both the effective address table and the TAGE update table.
 9. The multi-slice processor of claim 8, wherein the alignment between the effective address table and the TAGE update table is dependent upon each entry in the TAGE update table being mapped to a corresponding entry in the effective address table.
 10. The multi-slice processor of claim 8, wherein the multi-slice processor is further configured to carry out: generating, in dependence upon a mapping from an effective address table location to a TAGE update table location, the update information based on information from the effective address table location and on information from the TAGE update table location.
 11. The multi-slice processor of claim 10, wherein the update information is generated for the TAGE prediction unit without reading status information from the TAGE prediction unit.
 12. The multi-slice processor of claim 8, wherein the update information includes one or more of: a valid bit, a branch effective address, an indication as to whether a TAGE entry was hit, a TAGE component, a TAGE prediction, a TAGE usefulness indication, an alternative component, an alternative predication, a next component, and a next usefulness indication.
 13. The multi-slice processor of claim 12, wherein a prediction of whether a subsequent branch instruction is taken is made in dependence upon updating the TAGE branch prediction unit and the update information.
 14. The multi-slice processor of claim 8, wherein the effective address table stores effective addresses for instructions currently active, and wherein the TAGE update table stores information for branches corresponding to a TAGE update.
 15. An apparatus comprising: a plurality of execution slices, a tagged geometric history length (TAGE) branch prediction unit, wherein the multi-slice processor is configured to carry out: receiving, at an effective address table and at a TAGE update table, information for a branch instruction dispatched to an execution slice, wherein the effective address table and the TAGE update table are in alignment; responsive to the branch instruction being taken, updating the effective address table and the TAGE update table to indicate the branch instruction being taken; and updating, in dependence upon the alignment between the effective address table and the TAGE update table, the TAGE branch prediction unit with update information from both the effective address table and the TAGE update table.
 16. The apparatus of claim 15, wherein the alignment between the effective address table and the TAGE update table is dependent upon each entry in the TAGE update table being mapped to a corresponding entry in the effective address table.
 17. The apparatus of claim 15, wherein the multi-slice processor is further configured to carry out: generating, in dependence upon a mapping from an effective address table location to a TAGE update table location, the update information based on information from the effective address table location and on information from the TAGE update table location.
 18. The apparatus of claim 17, wherein the update information is generated for the TAGE prediction unit without reading status information from the TAGE prediction unit.
 19. The apparatus of claim 15, wherein the update information includes one or more of: a valid bit, a branch effective address, an indication as to whether a TAGE entry was hit, a TAGE component, a TAGE prediction, a TAGE usefulness indication, an alternative component, an alternative predication, a next component, and a next usefulness indication.
 20. The apparatus of claim 19, wherein a prediction of whether a subsequent branch instruction is taken is made in dependence upon updating the TAGE branch prediction unit and the update information. 